Skip to content

ci: build a console image and deploy it to the K3s cluster - #1

Merged
SeasonsChange422 merged 1 commit into
mainfrom
ci/deploy-to-k3s
Nov 11, 2026
Merged

SeasonsChange422 merged 1 commit into
mainfrom
ci/deploy-to-k3s

Conversation

@SeasonsChange422

Copy link
Copy Markdown
Member

Production moved from Docker on 207.57.124.102 to the K3s cluster (k3s.seasonschange.cn) on 2026-11-11. The service is already running there; this PR only changes how releases reach it.

Changes

  • New image job: builds deploy/Dockerfile and pushes docker.io/<DOCKER_USERNAME>/higress-console:<version>. The Dockerfile puts the console jar on top of the Higress all-in-one image, which is now pinned by digest instead of the server-local higress-aio-base:pinned tag (same digest 55f5fa3e…)
  • deploy job:
    1. Pre-pulls the image on the node with a throw-away pod. The Deployment uses Recreate, so this makes sure the running gateway is never stopped for an image the node cannot pull
    2. Applies deploy/k3s/higress.yaml and waits for console readiness, running rollout undo on failure
    3. Checks that mcp.tmlab.top still rejects unauthenticated MCP calls with 401
  • Adds deploy/k3s/higress.yaml, the manifest running in the cluster, and updates deploy/README.md

Verification

  • kubectl diff with the CI account: the only difference from the running Deployment is imagePullPolicy (Never → IfNotPresent)
  • The pre-pull step was tested with a good image (Succeeded) and a bad image (ErrImagePull)
  • Not yet tested end to end: the first real image build and push. It needs the org Docker Hub credentials, which can create tmllab/higress-console

Secrets

  • KUBE_CONFIG is set: a kubeconfig for ServiceAccount higress/ci-deployer
  • DEPLOY_HOST, DEPLOY_USER, DEPLOY_SSH_KEY and DEPLOY_KNOWN_HOSTS are no longer used

Note: merging triggers a deploy, because the workflow and deploy/** changed.

🤖 Generated with Claude Code

Higress moved from the Docker host 207.57.124.102 to the K3s cluster
(namespace higress). The workflow no longer uploads the jar over SSH and
builds the image on the server:

- image job: builds deploy/Dockerfile (console jar on top of the Higress
  all-in-one, now pinned by digest instead of a server-local tag) and pushes
  docker.io/<DOCKER_USERNAME>/higress-console:<version>
- deploy job: pre-pulls the image on the node with a throw-away pod so the
  Recreate rollout never stops the running gateway for an unpullable image,
  applies deploy/k3s/higress.yaml, waits for readiness, rolls back on failure
  and checks that mcp.tmlab.top still enforces auth
- add deploy/k3s/higress.yaml (the manifest running in the cluster) and
  update deploy/README.md
- needs repository secret KUBE_CONFIG (ServiceAccount higress/ci-deployer);
  DEPLOY_HOST/USER/SSH_KEY/KNOWN_HOSTS are no longer used

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SeasonsChange422
SeasonsChange422 merged commit 4919ec5 into main Nov 11, 2026
3 checks passed
@SeasonsChange422
SeasonsChange422 deleted the ci/deploy-to-k3s branch November 11, 2026 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant